ActivitySequenceProcess Element

This element in Transaction configuration allows Activities to be generated with an option to immediately attempt processing the generated Activities. Generation and the optional immediate processing will complete before the current Activity completes its processing. If the generated Activities are not configured to process immediately following activity generation, the Activities are only generated and left for a batch cycle or separate user execution.

ActivitySequenceProcess: Elements and Attributes
Element Attribute Parent Element Description
<ActivitySequenceProcess>   <Transaction>

Optional:

This section defines activity spawns through the Activity Sequence functionality.  
This feature allows the generation and, optionally, the execution of child activities before the parent activity completes. 

<ActivitySequence>   <ActivitySequenceProcess>

Required, Repeatable:

This section allows the user to name the Activity Sequence and provide the conditions upon which it will generate activities. All the generated activities within the <Activity> child elements contained by this element are part of the same sequence.  Activities of the same sequence must be generated and optionally processed before the next <ActivitySequence> element begins its generation and optional processing.

  NAME <ActivitySequence>

Required:

This provides a name to the sequence that can offer an ability to track the sequence's processing.

Values:

  • literal

  IF <ActivitySequence>

Optional:

This attribute allows configuration to provide the conditions that must evaluate to true to begin processing the sequence.  A false value skips all activities contained within this sequence from generation.  Processing then moves to the next <ActivitySequence> element.

Values:

  • conditional statement

<Activity>   <ActivitySequence>

Required, Repeatable:

This element provides a single transaction name to generate as an activity on the current entity or an array of activities to generate on the current entity or another entities.  An Activity array can spawn activities to other entities:  Client or Group Customer parent to Policy children, Policy parent to Client children, Company parent to Policy children, etc.  Generated activities may be processed within the processing scope of the parent Activity and delay the completion of the parent until all children have completed or simply use this sequence structure for a simple spawn without processing the child activities.

Values:

  • literal

    • This must be a valid transaction name available in the same context of the parent activity.

    • This will generate one Activity to the same entity as the parent Activity.

  • math variable

    • The variable must reference an activity array.

    • This will generate one or more Activities for the same entity instance or to different entity levels (Client level, Policy level) and different instances (individual Policies or Clients).

  PROCESSIMMEDIATE <Activity>

Required:

This attribute is the trigger to execute the child activities within the processing scope of the parent activity. 

Values:

  • No

    • Child activities are only generated. 

    • Processing these child activities is not attempted by the system. 

    • Child activity processing must be initiated by the user or a subsequent process.

  • Yes

    • Child activities are generated and these activities attempt processing within the scope of the current activity. 

    • The current activity remains in a processing status until all child activities have attempted and completed processing. 

    • The current activity must be successful, have no business or system errors, up to the point of reaching the Activity Sequence before any and all child activities generate and subsequently attempt processing. 

    • The eventual status of the current activity will reflect either successful completion of the current activity and all of its children, an error directly from the parent activity or a status indicating an issue with the complete success of one or more of all child activities.

  IF <Activity>

Optional:

This attribute allows configuration to provide the conditions to evaluate.  When the result is true, the process generates the <Activity> element's activities.  When false, activity processing skips generation of the <Activity> element's activities and moves to the next <Activity> element.

Values:

  • conditional statement

XML Schema

<Transaction>
...
    <ActivitySequenceProcess>
        <ActivitySequence NAME="[name]" IF="[condition]">
            <Activity PROCESSIMMEDIATE="[No | Yes]" IF="[condition]">[transaction name | activity array]</Activity>
            <Activity>...</Activity>
        </ActivitySequence>
        <ActivitySequence>...</ActivitySequence>
    </ActivitySequenceProcess>
...
</Transaction>

XML Example

<Transaction>
...
    <ActivitySequenceProcess>
        <ActivitySequence NAME="PolicyTrxB">
            <Activity PROCESSIMMEDIATE="Yes" IF="SelectOperationMV = 'Multiple'">BBBBBActivityArray</Activity>
        </ActivitySequence>
        <ActivitySequence NAME="PolicyTrxC">
            <Activity PROCESSIMMEDIATE="Yes" IF="SelectOperationMV = 'Multiple'">CCCCCActivityArray</Activity>
        </ActivitySequence>
    </ActivitySequenceProcess>
...
</Transaction>